Spyeye

Category: banking_trojan · Aliases: Trojan:Win32/SpyEye, Win32/SpyEye, Trojan.SpyEye, SpyEye Bot, TSPY_SPYEYE, SpyEye.A · Sample count (EMBER 2018): 192 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: Banking_TrojanStatus: Automated SignatureFirst seen: 2009Motivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
SpyEye (cataloged across security vendors as Trojan:Win32/SpyEye, Win32/SpyEye, and TSPY_SPYEYE) is one of the most notorious and commercially successful banking trojans in cybersecurity history, developed by Russian national Aleksandr Andreevich Panin ('Gribodemon') alongside co-conspirator Hamza Bendelladj ('Bx1').

Table of Contents

Overview

SpyEye (cataloged across security vendors as Trojan:Win32/SpyEye, Win32/SpyEye, and TSPY_SPYEYE) is one of the most notorious and commercially successful banking trojans in cybersecurity history, developed by Russian national Aleksandr Andreevich Panin ('Gribodemon') alongside co-conspirator Hamza Bendelladj ('Bx1'). First appearing on underground cybercrime forums in 2009, SpyEye was engineered to compete directly with and eventually assimilate the Zeus banking trojan codebase. Sold as a commercial crimeware kit, SpyEye utilized advanced Man-in-the-Browser (MitB) capabilities, HTML injection (webinjects), and keystroke logging to intercept financial credentials, one-time passwords, and payment card details as victims logged into online banking portals. The malware weaponized browser memory corruption flaws (including CVE-2010-0806 and CVE-2010-1885) and employed aggressive defense evasion routines, including a specialized 'Kill Zeus' component designed to remove rival Zeus botnet infections from compromised hosts. The botnet caused close to $1 billion in global financial damages before its operators were arrested and sentenced to over 24 years in federal prison in 2016.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Russian Banking Trojan Ecosystem

Known Derivatives & Downstream Variants: Spyeye 1.3 · Spyeye Zeus Merger · Spyeye.A · Spyeye.Gold

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-CACClipboard Access ControlIsolateT1115Isolate virtual desktop infrastructure (VDI) clipboards and alert on rapid background clipboard querying by non-foreground processes.
D3-CVHCredential Vault HardeningHardenT1555.003Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_SPYEYE_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Spyeye"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "spyeye" ascii wide nocase
        $s2 = "trojan:win32/spyeye" ascii wide nocase
        $s3 = "win32/spyeye" ascii wide nocase
        $s4 = "trojan.spyeye" ascii wide nocase
        $s5 = "spyeye bot" ascii wide nocase
        $s6 = "tspy_spyeye" ascii wide nocase
        $s7 = "spyeye.a" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Spyeye (Banking Trojan) Execution & Triage
id: 1f96448b-590f-594e-82cb-04470c32304e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Spyeye malware family. Detects recon staging, certutil file payload staging,
  and web-inject process proxying characteristic of banking trojan initial loaders.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/spyeye
- https://malware-families-catalog.systemhelpdesk.com/defensive/banking-trojan-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.banking-trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055
- attack.t1555_003
- attack.t1056_001
- attack.t1115
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \svchost.exe
    - \explorer.exe
    - \msiexec.exe
    - \certutil.exe
    CommandLine|contains:
    - -urlcache
    - -split -f
    - ipconfig /all
    - route print
    - netstat -ano
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_SPYEYE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Spyeye tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "spyeye" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Isolate infected banking workstations from all corporate and financial networks immediately.
  2. Terminate injected browser processes and remove hooked DLL modules from memory.
  3. Contact financial institutions to freeze compromised business accounts and monitor for fraudulent wire transfers.
  4. Perform an exhaustive password rotation across all online banking, accounting, and email accounts.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not conduct banking transactions from workstations showing signs of browser manipulation or unrecognized security certificates.
  2. Avoid clicking links in unsolicited banking or invoice notification emails.

References & External Analysis

Frequently Asked Questions

What is the SpyEye banking trojan?

SpyEye is a historic banking trojan and crimeware kit designed to hijack online banking sessions, intercept credentials, and automate unauthorized funds transfers.

Who were the primary creators of SpyEye?

SpyEye was developed by Russian national Aleksandr Andreevich Panin ('Gribodemon') and distributed with Algerian national Hamza Bendelladj ('Bx1'), both convicted by US federal courts in 2016.

How did SpyEye intercept banking credentials?

SpyEye hooked browser network APIs to perform Man-in-the-Browser attacks, injecting fake form fields (webinjects) into authentic banking web pages to capture sensitive data.

What was the relationship between SpyEye and Zeus?

Initially fierce commercial rivals—with SpyEye featuring a 'Kill Zeus' feature—the two codebases merged around late 2010 when the author of Zeus transferred source code to SpyEye's author.

Which vulnerabilities did SpyEye exploit for delivery?

Campaigns distributing SpyEye utilized exploit kits targeting browser and Windows flaws including CVE-2010-0806 and CVE-2010-1885.

How do I remove the Spyeye Banking_Trojan from Windows?

Manual removal of Spyeye is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Spyeye a virus or a Banking_Trojan?

Spyeye is classified as a Banking_Trojan. Unlike traditional viruses that infect files, modern malware like Spyeye typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Spyeye infection?

Symptoms of Spyeye can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Banking_Trojans

Want to prevent Spyeye and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/spyeye.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.